Back Out Plan Project Name TMH

Note to the Author

This document is a template for a Back Out that is to be completed during the Planning Phase of the ULC.

The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project:

Blue italicized text enclosed in angle brackets (<text>) provides instructions to the document author or indicates a field that should be replaced with information specific to a particular project.

Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

Purpose

<) The purpose of a Back Out Plan is to provide the documents all actions to be taken to restore the service if the associated change or release fails or partially fails. Back-out plans may provide for a full or partial reversal. This plan includes detailed steps and techniques for uninstalling a new system, as well reversing process changes. Specifically a Back-out Plan will include technical instructions and a communication plan that indicates who needs to be contacted, when, and how.>

Document Lifecycle

A Back-out Plan is required for all new development projects, and for maintenance releases. The creation of the Back-out Plan should be completed by the end of the Testing Phase. After review and approval of the Release Management Team, the final plan will be attached to the Change Control ticket for review by the Technical Change Control Board (TCCB).

Audience

The target audience for the Back-out Plan includes QA Release Management, Application Owner(s) , Project Manager(s), Technical Owner(s). These stakeholders will determine, the resources from their respective teams, who may be involved in developing the Back out Plan, as well as the final audience to obtain a copy of the Back Out Plan.

Roles and Responsibilities

The following stakeholders have a prescribed interest in the development, content, review and approval, and execution of the Back-out Plan:

Stakeholder	Interest
Project Manager	Ensures the Back-out Plan is appropriately developed. Monitors the actual implementation effort in accordance with the content of the Back Out Plan, and provides appropriate status reporting as needed.
Business Owner (s)	Contributes to the preparation of the Back Out Plan in collaboration with all applicable stakeholders to define the requirements, activities, and resources needed to execute the plan. . Approves the final Back-out Plan.
Technical Owner(s)	Contributes to the preparation of the Back Out Plan in collaboration with all applicable stakeholders to define the requirements, activities, and resources needed to execute the plan. . . Approves the final plan
QA Release Manager	Reviews the Back-out Plan to insure: All stakeholders have been fully represented in the development, review and approval of the documents All tasks have an assigned resource All dependencies are clearly identified Includes communication plan Includes contact information for key stakeholders and decision makers Once a plan has been completed, and approved by the appropriate parties, including QA Release Management, the QA Release Manager will provide representation of the final plan to the PRB and the TCCB.
Technical Change Control Board (TCCB)	Reviews the Back-out Plan. Provides additional feedback, as required.

Back Out Plan Details

<insert the details of your plan in this section. This may include a hyperlink to the actual detailed steps.>

Any change introduced into a production environment should have a properly documented back-out plan. A good back out plan will contain some or all of the following:

Detailed list of actions to be taken to reverse the roll out. This can be built using the Implementation Plan Template

Contact List, to include Decision makers, Application Owner(s), Technical Owners(s) and resources needed to execute the plan. Decision Maker is defined as the appropriate individuals to be involved in making the final decision to implement the Back Out Plan. This will often include senior level managers who may not be regular members of the Project Team.

A communications plan to keep all involved on the progress of the change, and estimated time to recovery

Key Stakeholders

Name	Role	Approver	Decision Maker

Appendix A: References

<Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.>

Table 1 below summarizes the documents referenced in this document.

Document Name	Description	Location
<Document name and version number>	<Document description>	<URL to where document is located>

Table 1 - Appendix A: References